Decoupling Design in Flutter →
GitHub issue →
We’re decoupling the Material and Cupertino design libraries from the core Flutter framework. Why? Because decoupling will empower the Flutter community to contribute to Material and Cupertino WITHOUT having to worry about how their contribution could become a regression in the framework.
Watch along and learn about the three phase approach the Flutter team is taking to decouple Material and Cupertino, what impact Flutter developers will experience during the transition, and what you need to do to ensure your apps keep running and keep your users happy.
Chapters:
0:00 - Intro
0:45 - The current state of Flutter, Material, Cupertino, and Widgets libraries
1:38 - The problem
5:03 - How we’re decoupling design in Flutter
8:08 -Timeline
9:30 - Impact on Flutter developers & apps
Watch more Flutter Flight Plans →
🔔 Subscribe to Flutter →
#Flutter
Speaker: Justin McCandless
Products Mentioned: Material, Cupertino, Flutter
|
Accelerators are getting faster, but is ...
For more details on this topic, visit th...
model that works best for your needs and...
Celebrate 10 years of Keras! 🎉 In this s...
Are you exploring JAX for the first time...
For more details on this topic, visit th...
Learn how Chrome handles permission upda...
CSS Selector Cheat Sheet: []( Web Dev Ro...
Building a recipe app? Stop worrying abo...
In this Python FastAPI tutorial, we'll b...
🔥AI-Powered Digital Marketing Certificat...
For only $1, you can claim a 1GB Residen...
WithSecure transformed threat analysis b...
🔥PGP in Generative AI and ML in collabor...
Looking to streamline your development p...